|
|
|
BlueCielo Meridian Enterprise 2012 System Requirements | BlueCielo ECM Solutions |
Content indexing is configurable on a per-vault basis. This task assumes that the vault should use the Windows content indexing component running on the Meridian application server. For other deployment options, see About Meridian deployment strategies.
Before you can configure content indexing, you must ensure that the appropriate content indexing component (Indexing Service or Windows Search, depending on the version of Windows) is running on the Meridian application server computer:
If a scheduled task will be created for maintaining content indexing, it will be helpful to know when other tasks are scheduled on the same computer so that this task can be scheduled to not interfere with those processes and vice versa. We recommend that this task be scheduled to occur after the day’s Prepare for Backup, recovery log, and regular system backup tasks occur.
Note Content index files can be re-created relatively easily in the case of loss and need not be backed up.
Note Although the Windows content indexing components run at a lower priority than other applications on the server and can be run during production hours, we recommend that it be scheduled to not run during production hours in order to maximize Meridian performance.
To configure content indexing for a vault:
Note Text searching from the Meridian client applications may be performed after the catalog is complete and available. View the Indexing Service branch in Computer Management to monitor the status of each vault’s content indexing catalog and to test searches.
Note If the vault content files are located on a device other than the Meridian Enterprise application server (for example, a SAN device or file server), the filtered text files must reside on the same server as the indexing service or they will not be added to the indexing catalog. To accomplish this, set the FullTextInLocalDataPath registry value described in HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\Installed DataStores. Although Meridian Enterprise supports content files residing at a UNC location, such a location is not supported for content indexing. That is, the content indexing service on a computer other than the Meridian Enterprise application server.
Note If a vault has a name longer than 40 characters, the corresponding Indexing Service catalog name will be abbreviated. Windows Indexing Service does not allow catalogs to have names longer than 40 characters. If you want to set a different catalog name than the default, set the FullTextCatalog registry value described in HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\Installed DataStores\<vaultname>.
Note To disable content indexing, clear the Enable content indexing for documents and memos option, remove the existing Indexing Service catalog, and delete the filtered text files.
Related concepts
Related tasks
Building and maintaining a content index
Accelerating content index creation
Copyright © 2000-2012 BlueCielo ECM Solutions |